Should I re-submit the RFE to allow DXL to modify deleted object values?
While the GUI always had attributes grayed out for deleted object, DXL had always been able to modify deleted object values and delete outgoing links. In v92 they removed that capability citing the previous ability we've had for 10 years a "bug", and citing that its inconsistent with the notion of a deleted object. My RFE to establish that ability, either universally or cleverly through options was rejected.
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=4894
We are now forced to undelete, modify, then re-delete such objects which adds history for that object and all its children. When in shared mode those children must be unlocked as well.
Some possible "clever" ways to restrict folks from doing this would be to
-
have some DB option set to prevent it, or
-
allow folks with RMDCA access to the object to do it, or
-
have some temporary flag set associated with the currently open module.
Do you have maintance DXL that now fails because of this? Scripts that control Links are subject to this restriction.
-Louie
I notice they failed to include this rather extensive "bug" fix in their release notes.
The ability to remove outlinks TO a deleted object is a separate issue. Although you technically cannot do that, its fairly common to make this mistake: Open Source and Target Exclusive. Delete the link and Delete the former target. Save the target module; close without saving the source module.
At first they also disallowed Attr-DXL from working on deleted objects, introduced that bug in v9201 and fixed it in v9203. Such DXL reported errors for deleted objects. So my Attr-DXL now has this:
if (isDeleted(obj) and length(doorsInfo(infoVersion)) >=7 and (((doorsInfo(infoVersion))[0:6] ==
"9.2.0.1") or (((doorsInfo(infoVersion))[0:6] ==
"9.2.0.0")))) halt
llandale - Mon Dec 19 11:58:42 EST 2011 |